POST Original File

Overview

---

The table below provides details on the POST method used to manage access control for an original file.

POST Original File
Method	POST
URL or Endpoint	/api/v1/projectId/audios/audioId/original-files
Headers	Authorization
Parameters	audioId, projectId
Request Body	accessControl

The description of the URL parameter is as follows:

URL Parameter Name	Mandatory	Type	Description
projectId	Yes	string	Unique Id of the project.
audioId	Yes	string	Unique id of the audio.

Request Body

{
  "accessControl": 1
}

Information about the fields that appear when you type in the request body are displayed in the table below.

Parameter Name	Mandatory	Type	Description
accessControl	Yes	integer	Access control level

## Response

{
  "success": true,
  "errors": [],
  "messages": [],
  "result": {
    "accessControl": 1
  },
  "resultInfo": "{resultInfo}",
  "statusCode": 200
}

Information about the fields that appear when you receive the response are displayed in the table below.

Top-Level Properties

Field Name	Type	Description
success	boolean	If the response is successful it will return true. Otherwise will return false
errors	array[string]	Indicates if there was an error
messages	array[string]	Returns the response message from back-end
result	object	Returns the response object
accessControl	integer	Access control level
resultInfo	string	Returns extra information about the result
statusCode	integer	Returns the HTTP Status Code

If the action is successful, the service sends back an HTTP 200 or 201 response.

Errors

For information about the errors that are common to all actions, see Common Errors:

• HTTP Status Code 400: Bad Request

• HTTP Status Code 401: Unauthorized

• HTTP Status Code 403: Forbidden

• HTTP Status Code 404: Result Not Found

• HTTP Status Code 500: Internal Server Error

• HTTP Status Code 503: Backend Fetch Failed